Connecting Repositories to one Integrated Domain

Information is the new commodity in global economy and trustworthy digital repositories will be key pillars within this ecosystem. The value of information only realised if these can interacted with a consistent manner their data accessible understandable globally. Establishing interoperability layer goal emerging domain Digital Objects. When considering how to proceed designing layer, it important state that need considered from two different perspectives: Repositories are reflection institutions make them operational (quality service, skilled experts, over many years, appropriate management procedures). computational services provide specific set functions. Complicating effort interoperable across existing have been developed past decades using wide range heterogeneous technologies, organisation functionality. Many own silos not interoperable. It realise much money has invested build therefore we cannot expect they large changes without great incentives funding. This heterogeneity core challenge making objects. paper focus on functional aspects proposes FAIR Object model as for describing use Interface Protocol (DOIP) establish communication all independently respective technical choices. conviction paper’s authors integration FDO DOIP performed minimal present examples document claim. We three paper: An B2SHARE A CORDRA repository Integration DOBES archive assigned Persistent Identifiers (PIDs) (Handles) its files. allows users add metadata according unified schema, but also possibility user communities extend schema. API one specify Handle which then gives access and/or bit sequences DO. should noted include bit-sequences being linked Handle. consists building proxy would interface streamline into single development was relatively simple did require any behalf repository. CNRI repository/registry/registration system manages DO, assigns Handles DOs through DOIP. For intents purposes, implements features Architecture. enables copying files or movíng In case (metadata sequences) CORDRA, example, functionality service such searching become possible. Important PID record identifying object extended point alternative path, offer paths client. latter aspect implemented. Moving DO result changing ownership adding updated about adaptation done yet, since some special functionalities, interesting discuss way could chosen. each bundle closely related objects treated object, i.e., separate reasons especially enabling contributors maintain control rights, tree structure allow organise criteria browse addition execute searches metadata. While accessing archival comparatively simple, ingest/upload feature more complex. supports establishing canonical resources define scopes authorisation (define who right grant permissions, etc.), facilitating lookup by supporting browsing criteria. Therefore, depositors where integrated, initial rights associated them. After uploading gathered workspace, carries out checks micro-workflow: checked against vocabularies partly curated, types aligned metadata, etc. operation called gatekeeper ensure highly despite (remote) people contributing content. Thus, requires 4 units specified: uploaded, bundle, node used default “open”. Adapting imply provides operations “ingest complex object”, “update metadata”, “add another bit-sequence “get me list operations”, “give client must do front-end interaction allowing required choose suitable operation. Then interact via starting, an external